| V-6656 | High | Unauthorized IP addresses are allowed Simple Network Management Protocol (SNMP) access to the SAN devices. | SNMP, by virtue of what it is designed to do, can be a large security risk. Because SNMP can obtain device information and set device parameters, unauthorized users can cause damage. Restricting... |
| V-6623 | High | Vendor supported, DOD approved, anti-virus software is not installed and configured on all SAN servers in accordance with the applicable operating system STIG on SAN servers and management devices and kept up-to-date with the most recent virus definition tables. | The SAN servers and other hosts are subject to virus and worm attacks as are any systems running an OS. If the anti-virus software is not installed or the virus definitions are not maintained on... |
| V-6608 | High | Hard zoning is not used to protect the SAN. | Risk: In a SAN environment, we potentially have data with differing levels or need-to-know stored on the same "system". A high level of assurance that a valid entity (user/system/process) of one... |
| V-6647 | High | The SAN fabric zoning lists are not based on a policy of Deny-by-Default with blocks on all services and protocols not required on the given port or by the site. | By using the Deny-by-Default based policy, any service or protocol not required by a port and overlooked in the zoning list will be denied access. If Deny-by-Default based policy was not used any... |
| V-6646 | High | The manufacturer’s default passwords have not been changed for all SAN management software. | The changing of passwords from the default value blocks malicious users with knowledge of the default passwords for the manufacturer's SAN Management software from creating a denial of service by... |
| V-6645 | High | All SAN management consoles and ports are not password protected. | Without password protection malicious users can create a denial of service by disrupting the SAN or allow the compromise of sensitive date by reconfiguring the SAN topography.
The IAO/NSO will... |
| V-6635 | Medium | Network management ports on the SAN fabric switches except those needed to support the operational commitments of the sites are not disabled. | Enabled network management ports that are not required expose the SAN fabric switch and the entire network to unnecessary vulnerabilities. By disabling these unneeded ports the exposure profile... |
| V-6636 | Medium | SAN management is not accomplished using the out-of-band or direct connection method. | Removing the management traffic from the production network diminishes the security profile of the SAN servers by allowing all the management ports to be closed on the production network.
The... |
| V-6631 | Medium | All the network level devices interconnected to the SAN are not located in a secure room with limited access. | If the network level devices are not located in a secure area they can be tampered with which could lead to a denial of service if the device is powered off or sensitive data can be compromised by... |
| V-6632 | Medium | Individual user accounts with passwords are not set up and maintained for the SAN fabric switch. | Without identification and authentication unauthorized users could reconfigure the SAN or disrupt its operation by logging in to the fabric switch and executing unauthorized commands.
The IAO/NSO... |
| V-6633 | Medium | The SAN must be configured to use bidirectional authentication. | Switch-to-switch management traffic does not have to be encrypted. Bidirectional authentication ensures that a rogue switch cannot be inserted and be auto configured to join the fabric. |
| V-6657 | Medium | The IP addresses of the hosts permitted SNMP access to the SAN management devices do not belong to the internal network. | SNMP, by virtue of what it is designed to do, can be a large security risk. Because SNMP can obtain device information and set device parameters, unauthorized users can cause damage. Therefore... |
| V-6619 | Medium | Prior to installing SAN components (servers, switches, and management stations) onto the DOD network infrastructure, components are not configured to meet the applicable STIG requirements. | Many SAN components (servers, switches, management stations) have security requirements from other STIGs. It will be verified that all requirement are complied with.
The IAO/NSO will ensure that... |
| V-6652 | Medium | Simple Network Management Protocol (SNMP) is used and it is not configured in accordance with the guidance contained in the Network Infrastructure STIG. | There are vulnerabilities in some implementations and some configurations of SNMP. Therefore if SNMP is used the guidelines found in the Network Infrastructure STIG in selecting a version of SNMP... |
| V-6613 | Medium | All security related patches are not installed. | Failure to install security related patches leaves the SAN open to attack by exploiting known vulnerabilities.
The IAO/NSO will ensure that all security-related patches are installed. |
| V-6610 | Medium | The SANs are not compliant with overall network security architecture, appropriate enclave, and data center security requirements in the Network Infrastructure STIG and the Enclave STIG | Inconsistencies with the Network Infrastructure STIG, the Enclave STIG, and the SAN implementation can lead to the creation of vulnerabilities in the network or the enclave. |
| V-6622 | Medium | Servers and other hosts are not compliant with applicable Operating System (OS) STIG requirements. | SAN servers and other hosts are hardware software combinations that actually run under the control of a native OS found on the component. This OS may be UNIX, LNIX, Windows, etc. The underlying... |
| V-6628 | Medium | A current drawing of the site’s SAN topology that includes all external and internal links, zones, and all interconnected equipment is not being maintained. | A drawing of the SAN topology gives the IAO and other interested individuals a pictorial representation of the SAN. This can be helpful in diagnosing potential security problems.
The IAO/NSO will... |
| V-6605 | Medium | The default zone visibility setting is not set to “none”. | If the default zone visibility setting is set to "none", new clients brought into the SAN will not be allowed access to any SAN zone they are not explicitly placed into.
The IAO/NSO will ensure... |
| V-6661 | Medium | Fabric switch configurations and management station configuration are not archived and/or copies of the operating system and other critical software for all SAN components are not stored in a fire rated container or are not collocated with the operational software. | .Backup and recovery procedures are critical to the security and availability of the SAN system. If a system is compromised, shut down, or otherwise not available for service, this could hinder... |
| V-7081 | Medium | SAN components are not configured with fixed IP addresses. | Without fixed IP address filtering or restricting of access based on IP addressing will not function correctly allowing unauthorized access to SAN components or creating a denial of service by... |
| V-6634 | Low | The fabric switches must use DoD-approved PKI rather than proprietary or self-signed device certificates. | DOD PKI supplies better protection from malicious attacks than userid/password authentication and should be used anytime it is feasible. |
| V-6637 | Low | Communications from the management console to the SAN fabric are not protected strong two-factor authentication. | Using two-factor authentication between the SAN management console and the fabric enhances the security of the communications carrying privileged functions. It is harder for an unauthorized... |
| V-6638 | Low | The manufacturer’s default PKI keys have not been changed prior to attaching the switch to the SAN Fabric. | If the manufacturer's default PKI keys are allowed to remain active on the device, it can be accessed by a malicious individual with access to the default key.
The IAO/NSO will ensure that the... |
| V-6639 | Low | The SAN is not configured to use FIPS 140-1/2 validated encryption algorithm to protect management-to-fabric communications. | The communication between the SAN management consol and the SAN fabric carries sensitive privileged configuration data. This data's confidentiality will be protected with FIPS 140-1/2 validate... |
| V-6609 | Low | SAN devices are not added to the site System Security Authorization Agreement (SSAA). | All hardware and software will be entered into the SSAA. This gives a central location where it can be shown that all interested parties have reviewed the impact on their security posture and... |
| V-6648 | Low | Attempts to access ports, protocols, or services that are denied are not logged.. | Logging or auditing of failed access attempts is a necessary component for the forensic investigation of security incidents. Without logging there is no way to demonstrate that the access attempt... |
| V-6660 | Low | End-user platforms are directly attached to the Fibre Channel network or access storage devices directly. | End-user platforms should only be connected to servers that run applications that access the data found on the SAN devices. SANs do not supply a robust user identification and authentication... |
